Skip to content

feat(cmn): hard stop on multiple exit signals#2378

Merged
mergify[bot] merged 2 commits intodevelopfrom
sc/cmn-max-signals
Mar 31, 2022
Merged

feat(cmn): hard stop on multiple exit signals#2378
mergify[bot] merged 2 commits intodevelopfrom
sc/cmn-max-signals

Conversation

@smartcontracts
Copy link
Contributor

Description
Adds a new feature to BaseServiceV2 to have a service exit immediately
when 3 exit signals are received. Useful when the main loop would take a
long time to exit but you want the service to exit immediately.

@changeset-bot
Copy link

changeset-bot bot commented Mar 30, 2022

🦋 Changeset detected

Latest commit: 786e93a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@eth-optimism/common-ts Patch
@eth-optimism/data-transport-layer Patch
@eth-optimism/message-relayer Patch
@eth-optimism/replica-healthcheck Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@tynes
Copy link
Contributor

tynes commented Mar 30, 2022

Looks like a circle ci error is breaking the tests, not exactly sure what is going on

Adds a new feature to BaseServiceV2 to have a service exit immediately
when 3 exit signals are received. Useful when the main loop would take a
long time to exit but you want the service to exit immediately.
@mergify mergify bot requested review from cfromknecht and tuxcanfly March 31, 2022 19:03
@mergify mergify bot merged commit e36b085 into develop Mar 31, 2022
@mergify mergify bot deleted the sc/cmn-max-signals branch March 31, 2022 20:25
@mslipper mslipper mentioned this pull request Apr 1, 2022
nebojsa94 pushed a commit to Tenderly/optimism that referenced this pull request Apr 26, 2022
Adds a new feature to BaseServiceV2 to have a service exit immediately
when 3 exit signals are received. Useful when the main loop would take a
long time to exit but you want the service to exit immediately.

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
theochap added a commit that referenced this pull request Dec 10, 2025
)

## Description

Rewire the sequencer unsafe payload sender from the engine to the
network.

Previously, the sequencer was sending the unsafe blocks it received from
the network `BuildTask` back to the network to call `InsertUnsafeTask`.
Since the `BuildTask` inserts the newly built payloads to the engine
state (like what the `InsertUnsafeTask` would do), this resulted in a
no-op.

Instead, the sequencer should send the payloads to the network to gossip
them to the p2p mesh.

## Misc

Close #2244
Built on top of #2376
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants